table of contents
GIT-REVERT(1) | Git Manual | GIT-REVERT(1) |
NAME¶
git-revert - Revert an existing commit
SYNOPSIS¶
git revert [--edit | --no-edit] [-n] [-m parent-number] [-s] <commit>
DESCRIPTION¶
Given one existing commit, revert the change the patch introduces, and record a new commit that records it. This requires your working tree to be clean (no modifications from the HEAD commit).
Note: git revert is used to record a new commit to reverse the effect of an earlier commit (often a faulty one). If you want to throw away all uncommitted changes in your working directory, you should see git-reset(1), particularly the --hard option. If you want to extract specific files as they were in another commit, you should see git-checkout(1), specifically the git checkout <commit> — <filename> syntax. Take care with these alternatives as both will discard uncommitted changes in your working directory.
OPTIONS¶
<commit>
-e, --edit
-m parent-number, --mainline parent-number
Reverting a merge commit declares that you will never want the tree changes brought in by the merge. As a result, later merges will only bring in tree changes introduced by commits that are not ancestors of the previously reverted merge. This may or may not be what you want.
See the revert-a-faulty-merge How-To[1] for more details.
--no-edit
-n, --no-commit
This is useful when reverting more than one commits´ effect to your index in a row.
-s, --signoff
AUTHOR¶
Written by Junio C Hamano <gitster@pobox.com[2]>
DOCUMENTATION¶
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org[3]>.
GIT¶
Part of the git(1) suite
NOTES¶
- 1.
- revert-a-faulty-merge How-To
- 2.
- gitster@pobox.com
- 3.
- git@vger.kernel.org
02/03/2020 | Git 1.7.1 |